chore: update repository URL to callstackincubator org#51
Merged
Conversation
Fixes OIDC canary publish failures — npm's trusted publishing validates the repo in the provenance claim against the package's repository field, which still pointed to the old piotrski/ location. Also updates skill install commands in README. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
repository.urlinpackage.jsonfrompiotrski/agent-react-devtoolstocallstackincubator/agent-react-devtoolsREADME.mdto matchWhy
npm's OIDC trusted publishing validates the repository in the provenance claim against the
repositoryfield inpackage.json. Since the package moved to thecallstackincubatororg but the field wasn't updated, every canary publish attempt fails withENEEDAUTHthe OIDC claims don't match what npmjs.com expects.